Extended qos support in epc

ABSTRACT

Example embodiments presented herein are directed towards a target Mobility Management Entity (MME) or a target Serving General Packet Radio Service Support Node (SGSN) network node, and method, for handling a mobility procedure or session procedure within the same operator. The roaming agreement handling may comprise comparing a Quality of Service (QoS) parameter associated with a source system, a maximum QoS associated with a target system and a Packet Data Network Gateway (PGW) or Policy and Changing Rules Function (PCRF) capability. The mobility procedure or session procedure handling may further comprise providing instructions for the roaming procedure based on the comparison. 
     Example embodiments may further comprise a Packet Data Network Gateway (PGW) network node, and method, for adjusting Quality of Service (QoS) during a mobility procedure or session procedure. The adjustment may be based on a received target maximum QoS.

RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application No.61/422,276, filed on Dec. 13, 2010. This application is also acontinuation of International Application No. PCT/EP2011/072220, filedon Dec. 8, 2011, which also claims priority to U.S. ProvisionalApplication No. 61/422,276, filed on Dec. 13, 2010. The entire teachingsof the above applications are incorporated herein by reference.

BACKGROUND

In a typical cellular system, also referred to as a wirelesscommunications network, wireless terminals, also known as mobilestations and/or user equipment units communicate via a Radio AccessNetwork (RAN) to one or more core networks. The wireless terminals canbe mobile stations or user equipment units such as mobile telephonesalso known as “cellular” telephones, and laptops with wirelesscapability, e.g., mobile termination, and thus can be, for example,portable, pocket, hand-held, computer-comprised, or car-mounted mobiledevices which communicate voice and/or data with radio access network.

The radio access network covers a geographical area which is dividedinto cell areas, with each cell area being served by a base station,e.g., a Radio Base Station (RBS), which in some networks is also called“NodeB” or “B node” and which in this document also is referred to as abase station. A cell is a geographical area where radio coverage isprovided by the radio base station equipment at a base station site.Each cell is identified by an identity within the local radio area,which is broadcast in the cell. The base stations communicate over theair interface operating on radio frequencies with the user equipmentunits within range of the base stations.

In some versions of the radio access network, several base stations aretypically connected, e.g., by landlines or microwave, to a Radio NetworkController (RNC). The radio network controller, also sometimes termed aBase Station Controller (BSC), supervises and coordinates variousactivities of the plural base stations connected thereto. The radionetwork controllers are typically connected to one or more corenetworks.

The Universal Mobile Telecommunications System (UMTS) is a thirdgeneration mobile communication system, which evolved from the GlobalSystem for Mobile Communications (GSM), and is intended to provideimproved mobile communication services based on Wideband Code DivisionMultiple Access (WCDMA) access technology. UMTS Terrestrial Radio AccessNetwork (UTRAN) is essentially a radio access network using widebandcode division multiple access for user equipment units (UEs). The ThirdGeneration Partnership Project (3GPP) has undertaken to evolve furtherthe UTRAN and GSM based radio access network technologies. Long TermEvaluation (LTE) together with Evolved Packet Core (EPC) is the newestaddition to the 3GPP family.

Mobility management is an important function in maintaining cellularnetworks. The goal of mobility management is to track where cellularphones, or user equipments, are located in order for mobile phoneservices to be provided to the various user equipments comprised in anygiven network. The network nodes which are primarily responsible formobility management are the Mobility Management Entity (MME) and theServing General Packet Radio Service Support Node (SGSN).

SUMMARY

Current 3GPP specifications only allow for the MME/S4-SGSN to downgradesubscribed-ARP and APN-AMBR received from the HSS before forwarding thisinformation to the SGW and onwards to the PGW during attach. In 3GPP, itis not clear how to handle mobility procedures, other than Attach, foruser equipment requests (e.g., a standalone user equipment requested PDNconnectivity request). In the present specification the HPLMN should notupgrade bearer level QoS or APN-AMBR above this provided value during aTracking Area Update, Routing Area Update or a handover procedure orthere will be a risk that the MME or SGSN will reject the bearerestablishment or even detach the user equipment.

Thus, an object of the example embodiments presented herein may be toprovide improved handling of mobility procedures or session procedures.Accordingly, some of the example embodiments may be directed towards amethod in a target Mobility Management Entity (MME) or a target ServingGeneral Packet Radio Service Support (SGSN) node for handling a mobilityprocedure or session procedure, the target MME node or the target SGSNnode being comprised in a radio network. The method comprises receiving,from a source MME node or a source SGSN node, a communication messagecomprising a QoS parameter associated with a source serving networksystem. The communication message further comprises a Packet DataNetwork Gateway (PGW) or a Policy and Charging Rules Function (PCRF)capability information element, where the capability information elementindicates if a PGW or PCRF node supports maximum QoS handling. Themethod further comprises comparing a maximum allowed QoS of a targetserving network, the QoS parameter associated with the source servingnetwork and the capability information element. The method alsocomprises providing instructions for the mobility procedure or sessionprocedure for each Packet Data Network (PDN) connection associated witha requesting user equipment, the instructions being based the comparing.

Some example embodiments may be directed towards a method in a PacketData Network Gateway (PGW) node for adjusting Quality of Service (QoS)during a mobility procedure or session procedure, the PGW node beingcomprised in a radio network. The method comprises receivinginstructions, from a target Mobility Management Entity (MME) or a targetServing General Packet Radio Service Support Node (SGSN), for adjustingan allowed QoS associated with a PDN connection of a user equipmentrequesting the mobility procedure or session procedure. The instructionscomprise a maximum allowed QoS of a target serving network and a QoSparameter associated with a source serving network. The method alsocomprises adjusting a QoS associated with the PDN connection of the userequipment based on the maximum allowed QoS of the target serving networkand the QoS parameter associated with the source serving network.

Some example embodiments may be directed towards a target MobilityManagement Entity (MME) or a target Serving General Packet Radio ServiceSupport (SGSN) node for handling a mobility procedure or sessionprocedure, the target MME node or the target SGSN node being comprisedin a radio network. The node comprises a receiving port configured toreceive, from a source MME node or a source SGSN node, a communicationmessage comprising a QoS parameter associated with a source servingnetwork system. The communication message further comprises a PacketData Network Gateway (PGW) or a Policy and Charging Rules Function(PCRF) capability information element, where the capability informationelement indicates if a PGW or PCRF node supports maximum QoS handling.The node further comprises a comparing unit configured to compare amaximum allowed QoS of a target serving network, the QoS parameterassociated with the source serving network and the capabilityinformation element. The node also comprises an instructions unitconfigured to provide instructions for the mobility procedure or sessionprocedure for each Packet Data Network (PDN) connection associated witha requesting user equipment, the instructions being based on thecomparison.

Some example embodiments may also be directed towards a Packet DataNetwork Gateway (PGW) node for adjusting Quality of Service (QoS) duringa mobility procedure or session procedure, the PGW node being comprisedin a radio network. The node comprises a receiving port configured toreceive instructions, from a target Mobility Management Entity (MME) ora target Serving General Packet Radio Service Support Node (SGSN), foradjusting an allowed QoS associated with a PDN connection of a userequipment requesting the mobility procedure or session procedure. Theinstructions comprise a maximum allowed QoS of a target serving networkand a QoS parameter associated with a source serving network. The nodefurther comprises an adjusting unit configured to adjust a QoSassociated with the PDN connection of the user equipment based on themaximum allowed QoS of the target serving network and the QoS parameterassociated with the source serving network.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing will be apparent from the following more particulardescription of the example embodiments, as illustrated in theaccompanying drawings in which like reference characters refer to thesame parts throughout the different views. The drawings are notnecessarily to scale, emphasis instead being placed upon illustratingthe example embodiments.

FIGS. 1 and 2 are schematic examples of wireless networks;

FIG. 3 is an illustrative example of a mobility procedure;

FIG. 4 is an illustrative example of a mobility procedure, according tosome of the example embodiments;

FIG. 5 is a schematic of a MME or a S4-SGSN network node, according tosome of the example embodiments;

FIG. 6 is a schematic of a PGW network node, according to some of theexample embodiments;

FIG. 7 is a flow diagram depicting example operational steps which maybe taken by the MME of the S4-SGSN network node of FIG. 5, according tosome of the example embodiments; and

FIG. 8 is a flow diagram depicting example operational steps which maybe taken by the PGW network node of FIG. 6, according to some of theexample embodiments.

DETAILED DESCRIPTION

In the following description, for purposes of explanation and notlimitation, specific details are set forth, such as particularcomponents, elements, techniques, etc. in order to provide a thoroughunderstanding of the example embodiments. However, it will be apparentto one skilled in the art that the example embodiments may be practicedin other manners that depart from these specific details. In otherinstances, detailed descriptions of well-known methods and elements areomitted so as not to obscure the description of the example embodiments.The terminology used herein is for the purpose of describing the exampleembodiments and is not intended to limit the embodiments presentedherein.

FIG. 1 shows a schematic view of a first system 100 in which some of theexample embodiments may be applied. The system 100 is a so called 2G/3Gsystem, also sometimes referred to as a GERAN/UTRAN system. As shown,the system 100 can accommodate a number of user equipments one of whichis shown as an example, with the reference number 130. Naturally, thesystem 100 can accommodate a large number of user equipments and is notlimited to accommodating only one user equipment.

All traffic to and from the user equipment 130 is routed via a so called“base station”, which, depending on the nature of the system, hasdifferent names. In the case of a GERAN/UTRAN system such as the one inFIG. 1, the base station is in this text referred to by the generic name“Radio Base Station”, here and in FIG. 1 abbreviated as RBS. The RBSwhich the user equipment 130 is connected to is shown in FIG. 1 as RBS128. One example of a system specific name for an RBS is NodeB, as usedin 3G systems, and another example is BTS, Base Transceiver System, asused in some 2G systems.

Regardless of the kind of system, the mobility of the user equipment 130is controlled by what will here initially be referred to generically asa “mobility management node”, which, as shown in FIG. 1, in the case ofGERAN/UTRAN is a so called S4-SGSN, shown as 125 in FIG. 1.

The “mobility management node” is connected to a Serving Gateway, an SGW115, which in turn is connected to a PDN Gateway, PGW 110. The PGW 110can be connected to a unit or a function for Policy and Charging RulesFunction, a so called PCRF 105, or the PGW 110 can be arranged to takecertain policy and charging actions on its own without the use of aPCRF.

FIG. 2 shows a schematic overview of a second system 200 in which theinvention can be applied. The system 200 is a so called LTE basedsystem, also referred to as an EUTRAN system. It should be pointed outthat the terms “LTE” and “LTE based” system is here used to include bothpresent and future LTE based systems, such as, for example, advanced LTEsystems.

In a EUTREAN system such as the one 200 in FIG. 2, the “base station” isreferred to as an eNodeB, shown as 129 in FIG. 2. The “mobilitymanagement node” is in a EUTRAN system referred to as a MobilityManagement Entity (MME) shown as 120 on FIG. 2. The SGW and PGW of thesystem in FIG. 2 are similar to those in FIG. 1, and will for thatreason not be described again here, which is also the case for the PCRF105.

It should be appreciated that although FIG. 1 shows a system 100 whichis a GERAN/UTRAN system and FIG. 2 shows a system 200 which is an EUTRANsystem, the invention can also be applied in systems which combine thesetwo technologies, i.e. combined GERAN/UTRAN and EUTRAN systems.

Example embodiments are presented herein to provide improved handlingduring mobility procedures in radio networks. As a part of the solutionaccording to the example embodiments discussed herein, problems withcurrent solutions will be identified and discussed.

FIG. 3 illustrates a mobility procedure which may occur in any of thewireless systems shown in FIG. 1 or 2. As shown in FIG. 3, a userequipment 130 may be associated with a source serving system featuring asource MME 120 or S4-SGSN 125. During a mobility procedure (e.g., ahandover procedure) the user equipment 130 may move to a target system.The target system may comprise a target MME 121 or a target S4-SGSN 126.

In establishing a connection with the target system, the source MME 120or the source S4-SGSN 125 may send a communication message to the targetMME 121 or the target S4-SGSN 126 (message 1). The communication messagemay comprise a maximum QoS associated with the source MME 120 or thesource S4-SGSN 125. The target MME 121 or the target S4-SGSN 126 maythereafter evaluate the maximum QoS associated with the source systemwith the QoS capabilities of the target MME 121 or the target S4-SGSN126.

If the maximum QoS associated with the target MME 121 or the targetS4-SGSN 126 is lower or higher than the maximum QoS associated with thesource MME 120 or the source S4-SGSN 125, the target MME 121 or thetarget S4-SGSN 126 may send a request to the PGW or PCRF network node,via the SGW network node, to see if the QoS parameters of the targetsystem may be re-authorized (messages 2 and 3). If the PGW is unable tosupport the QoS level, than the mobility procedure will be stopped.

At least two things are missing in the current specification. First,when a user equipment moves from one operator's network (e.g., a sourcenetwork) to another operator's network (e.g., a target network) withoutloosing connectivity (e.g., during S1-based EUTRAN handover or athandover between E-UTRAN, UTRAN and GERAN) the present 3GPP standardslacks the means for the target operator network to communicate themaximum allowed QoS that is in-line with roaming agreements with the PGW(and the PCRF for the case of a dynamic PCC being deployed).

Second, the scenario of when the maximum allowed QoS that can berequested by a HPLMN operator (e.g., a source maximum QoS) exceeds thesubscribed QoS of a user equipment (e.g., a target maximum QoS) iscurrently not specified in the 3GPP standard. In the presentspecification, a MME may downgrade a subscribed QoS before sendingroaming procedure communications to the SGW and PGW network nodes. Ifthe subscribed QoS (target) is lower than the maximum allowed QoS(source) of the serving network, the present 3GPP standard lacks themeans for the VPLMN operator to unambiguously communicate both thesubscribed QoS of the end user and the maximum allowed QoS of theserving network to the HPLMN core network.

For example, if the maximum allowed APN-AMBR that a roaming user may beassigned is 10 Mbps in a VPLMN but the subscribed APN-AMBR is 2 Mbps,then the MME, in the VPLMN, can not indicate to the HPLMN the maximum of10 Mbps by changing the subscribed QoS since the subscribed QoS isalready lower than 10 Mbps.

In addition, the general lack of QoS re-negotiation functionality in theEPC has a major disadvantage also for non-roaming cases. When aPDN-connection is handed over from one system, e.g., EUTRAN to anothersystem, UTRAN or GERAN, it is not certain that the target system canactually support the QoS of the bearers in that PDN-connection. Forexample, the data rates of LTE-advanced (specified in 3GPP release 10)are superior to the data rates of ordinary LTE (specified in 3GPPrelease 8 and release 9), not to mention the possible data rates ofHSPA, UMTS and GPRS. In a mobility scenario from a source system wheresuperior data rates are supported to a target system with lower QoScapabilities, the target system will not be able to establish therequired bearers. Since QoS negotiations are not supported in the EPC,the target system may have no other option but to either deactivate thebearers with too high QoS or alternatively to reject the handoverprocedure. As a consequence bearers will be lost or the user may even bedetached.

Other examples of specific problems with user equipment roaming may alsoinclude an user equipment moving from an old or source MME/S4-SGSN to anew or target MME/S4-SGSN, where it may not be possible to reflect tothe target MME/S4-SGSN if the PGW, and optionally PCRF, supports themaximum allowed QoS value or not. Therefore, the target MME/S4-SGSN willtry to send maximum allowed QoS, which may be configured in the targetMME/S4-SGSN, in different control messages towards PGW/PCRF. In somesituations, the target MME/S4-SGSN will reject the control procedurebecause some of the selected QoS values are above the target maximumallowed QoS values.

Furthermore, there is no use for the target MME/S4-SGSN to send themaximum allowed QoS to the PGW/PCRF network node, if the maximum allowedQoS is not supported by PGW/PCRF. For this situation a reject by thetarget MME/S4-SGSN may occur.

If the maximum allowed QoS, configured in the target MME/S4-SGSN, isdifferent than the values used by the PGW/PCRF, there is no use for thetarget MME/S4-SGSN to send the maximum allowed QoS to the PGW/PCRF ifthe maximum allowed QoS is not supported by the PGW/PCRF. Thus, theremay not be a reason for the target MME/S4-SGSN to send the maximumallowed QoS to PGW/PCRF during following procedures, for example:

-   -   Attach in 3GPP TS 23.401;    -   User equipment requested PDN Connectivity in 3GPP TS 23.401;    -   Primary PDP Context activation in 3GPP TS 23.060;    -   Routing Area Update procedures and Tracking Area Update        procedures such as:        -   RAU and TAU procedures with and without SGW change in 3GPP            TS 23.401; and        -   RAU procedure in 3GPP TS 23.401;        -   RAU procedures in 3GPP TS 23.060;    -   Gn/Gp-SGSN to MME TAU in 3GPP TS 23.401;    -   Handover procedures such as:        -   S1 based handover procedure and RAT handover procedure, both            with and without SGW change in 3GPP TS 23.401; and        -   3G SGSN (Gn/Gp-SGSN) to MME combined hard handover and SRNS            relocation procedure in 3GPP TS 23.401;        -   MME to 3G SGSN (Gn/Gp-SGSN) combined hard handover and SRNS            relocation procedure in 3GPP TS 23.401    -   S4-SGSN based SRNS relocation procedure in 3GPP TS 23.060; and    -   PS handover procedure in 3GPP TS 43.129.

Thus, example embodiments presented herein solve the above mentionedproblems and provide improved handling in mobility procedures. FIG. 4illustrates a mobility procedure according to some of the exampleembodiments.

First, a PGW or PCRF capability or the PGW/PCRF support of max allowedQoS feature may be sent from a PCRF or a PGW 110 to a MME 120 or S4-SGSN125 in, for example, s5/s8 and s11/s4 interfaces (messages 1 and 2). ThePGW or PCRF capability may indicate if the PGW or the PCRF may supportQoS handling according to some of the example embodiments. As anexample, the PGW/PCRF capability may be sent in the following messagesCreate Session Response, Modify Bearer Response, Create Bearer Response,Update Bearer Request and/or Delete Bearer Request. It should beappreciated that the PGW/PCRF capability may be sent in the form of aninformation element or any other equivalent form known in the art.

Thereafter, the MME120 or the S4-SGSN 125 may store the PGW/PCRFcapability information element to be utilized when a user equipmentmoves to another MME or S4-SGSN during a mobility procedure (message 3).

Once a mobility request is made by a user equipment 130 (e.g., using aTracking Area Update procedure, Routing Area Update procedure, or a S1based handover procedure) (message 4) the source MME 120 or the sourceS4-SGSN 125 may forward the PGW/PCRF capability information element to atarget MME 121 or a target S4-SGSN 126, for example, in s3, s10 and s16interfaces (message 5). The PGW/PCRF capability information element maybe sent in the following massages Context Response/SGSN ContextResponse, Identity Response, or a Forward Relocation Request.

The target MME 121 or the target S4-SGSN 126 may send to the PGW 110,via the SGW 115, the maximum allowed QoS in the target system, forexample, in s11/S4 interfaces (messages 6 and 7). The target maximumallowed QoS may be sent in the following massages Modify Bearer Request(for the case when there is no SGW change) or Create Session Request(for the case when there is a SGW change).

Whether the target maximum allowed QoS is included in the s11/S4messages or not may depend on the received PGW/PCRF capabilityinformation element. For example, if the PGW/PCRF capability informationelement indicates QoS handling is not supported by the PGW/PCRF, theremay not be a need to include the target maximum allowed QoS in a messageto the PGW/PCRF.

Thus, via message 7, the SGW 115 may, based on the target maximumallowed QoS, change (if the S4-SGSN/MME has been changed) trigger s5/s8signaling (i.e., a Modify Bearer Request comprising the target maximumallowed QoS to PGW/PCRF). This s5/s8 signaling is a new SGW behavior andis not stated in the 3GPP standard. The reason for sending the new ortarget maximum allowed QoS value, which may be defined in the targetS4-SGSN/MME, is to let the PGW/PCRF have the new maximum allowed QoSwhich is valid in this serving network. It should be appreciated thatthe evaluation procedure described above may be made for each PDNconnection associated with the user equipment 130 involved in theroaming procedure. This separate evaluation may be useful as each PDNconnection may be a different associated QoS value.

FIG. 5 is an illustrative example of a target MME 121 or a targetS4-SGSN 126 network node according to some of the example embodiments.The network node 121/126 may comprise any number of communication ports,for example a receiving port 307 and a transmitting port 308. Thecommunication ports may be configured to receive and transmit any formof communications data. It should be appreciated that the network node121/126 may alternatively comprise a single transceiver port. It shouldfurther be appreciated that the communication or transceiver port may bein the form of any input/output communications port known in the art.

The network node 121/126 may further comprise at least one memory unit309. The memory unit 309 may be configured to store received,transmitted, and/or measured data of any kind and/or executable programinstructions. The memory unit 309 may be any suitable type of computerreadable memory and may be of a volatile and/or non-volatile type.

The network node 121/126 may also comprise a comparing unit 315 that maybe configured to compare QoS capabilities of a target and source system,as well as PGW/PCRF capabilities. The network node 121/126 may alsocomprise an instructions unit 317 that may be configured to provideinstructions regarding the handling of a mobility procedure. The networknode 121/126 may further comprise a general processing unit 311.

It should be appreciated that the comparing unit 315, the instructionsunit 317 and/or the processing unit 311 may be any suitable type ofcomputation unit, e.g. a microprocessor, digital signal processor (DSP),field programmable gate array (FPGA), or application specific integratedcircuit (ASIC). It should also be appreciated that the comparing unit315, the instructions unit 317 and/or the processing unit 311 need notbe comprised as separate units. The comparing unit 315, the instructionsunit 317 and/or the processing unit 311 may be comprised as a singlecomputational unit or any number of units.

FIG. 6 is an illustrative example of a PGW 110 network node according tosome of the example embodiments. The network node 110 may comprise anynumber of communication ports, for example a receiving port 407 and atransmitting port 408. The communication ports may be configured toreceive and transmit any form of communications data. It should beappreciated that the network node 110 may alternatively comprise asingle transceiver port. It should further be appreciated that thecommunication or transceiver port may be in the form of any input/outputcommunications port known in the art.

The network node 110 may further comprise at least one memory unit 409.The memory unit 409 may be configured to store received, transmitted,and/or measured data of any kind and/or executable program instructions.The memory unit 409 be any suitable type of computer readable memory andmay be of a volatile and/or non-volatile type.

The network node 110 may also comprise an adjusting unit 415 that may beconfigured to adjust QoS capabilities associated with a target system.The network node 110 may further comprise a general processing unit 411.

It should be appreciated that the adjusting unit 415 and/or theprocessing unit 411 may be any suitable type of computation unit, e.g. amicroprocessor, digital signal processor (DSP), field programmable gatearray (FPGA), or application specific integrated circuit (ASIC). Itshould also be appreciated that the adjusting unit 415 and/or theprocessing unit 411 need not be comprised as separate units. Theadjusting unit 415 and/or the processing unit 411 may be comprised as asingle computational unit or any number of units.

FIG. 7 is a flow diagram depicting example operations which may be takenby the target MME 121 or the target S4-SGSN 126 network node of FIG. 5.FIG. 8 is a flow diagram depicting example operations which may be takenby the PGW 110 network node of FIG. 6. Example operations 41-51 areperformed by the target MME 121 or the target S4-SGSN 126 network node.Example operations 57 and 59 are performed by the PGW 110 network node.

Example Operation 41

According to some of the example embodiments, the target MME 121 or thetarget S4-SGSN 126 network node is configured to receive 41, from asource MME 120 or a source S4-SGSN 125 network node, a communicationsmessage comprising QoS parameter associated with a source servingnetwork system. The communication message further comprises a PGW and/ora PCRF capability information element. The capability informationelement indicates a PGW of PCRF capability to support maximum allowedQoS handling. An example of such a communication message may be message5 of FIG. 4. The QoS parameter associated with the source servingnetwork may be a maximum allowed QoS of the source serving networksystem and/or an authorized QoS of the source serving network system.The receiving port 307 is configured to perform the receiving 41. Itshould be appreciated that maximum allowed QoS handling may be theability, of the PGW and/or PCRF node, not to authorize a QoS, of a PDNconnection of a requesting user equipment, which higher than the maximumallowed QoS of the serving network.

Example Operation 43

According to some of the example embodiments, the target MME 121 or thetarget S4-SGSN 126 network node is further configured to compare 43 amaximum allowed QoS of a target serving network, the QoS parameterassociated with the source serving network and the capabilityinformation element. The comparing unit 315 is configured to perform thecomparing 43.

It should be appreciated that the maximum allowed QoS of the targetserving network may be stored locally in the target MME 121 or thetarget S4-SGSN 126. It should also be appreciated that the maximumallowed QoS of the target serving network may also be retrieved from anyother source in the radio network (e.g., a RNC, BSS or eNB networknode).

Example Operation 47

According to some of the example embodiments, the target MME 121 or thetarget S4-SGSN 126 network node is further configured to provide 47instructions for the mobility procedure or session procedure for eachPacket Data Network connection associated with a requesting userequipment, the instructions being based on the comparing 43. It shouldfurther be appreciated that the target node may be a Gn/Gp-SGSN. Theinstructions unit 317 is configured to perform the providing.

It should be appreciated that the mobility procedure or sessionprocedure may be a Roaming Area Update, a Tracking Area Update, aHandover procedure, Attach, PDN Connectivity or primary PDP contextactivation.

Example Operation 49

According to some of the example embodiments, the providing 47 mayfurther comprise allowing 49 the mobility procedure of session procedurewith an indication that a QoS adjustment is needed if the maximumallowed QoS of the target serving network and the QoS parameterassociated with the source serving network do not equal. Theinstructions unit 317 may be configured to perform the allowing 49.

It should be appreciated that the allowing 49 may occur if thecapability information element indicates that the PGW/GGSN or the PCRFnode supports maximum allowed QoS handling, or if the source MME or thesource SGSN or source SGW node does not support the capability element.For example, in the case of legacy systems, the PGW/GGSN, PCRF, MME, orSGSN may not support the maximum allowed QoS functionality describedherein.

Example Operation 51

According to some of the example embodiments, the allowing 49 mayfurther comprising sending 51, to the PGW 110 node, the maximum allowedQoS of the target serving network. The transmitting port 308 may beconfigured to perform the sending 51. It should be appreciated that theinformation may be sent in the form of a communications message, forexample messages 6 and 7 of FIG. 4. It should further be appreciatedthat the sending may further comprise sending the maximum allowed QoS ofthe target serving network to PGW directly or to PGW, via a SGW node, orGGSN node via Gn/Gp-SGSN.

Example Operation 53

According to some of the example embodiments, the allowing 49 mayfurther comprise adjusting 53, in the PGW/GGSN node, an allowed QoSassociated with a PDN connection of the requesting user equipment basedon the maximum allowed QoS of the target serving network. An adjustmentunit 415 may be configured to perform the adjusting 53.

Example Operation 55

According to some of the example embodiments, the providing 47 mayfurther comprise rejecting 55 the mobility procedure or the sessionprocedure if the QoS parameter associated with the source servingnetwork is higher than the maximum allowed QoS of the target servingnetwork, and the capacity information element indicates that thePGW/GGSN or the PCRF node does not support maximum QoS handling. Theinstructions unit 317 may be configured to perform the rejecting 55.

Example Operation 57

According to some of the example embodiments, the providing 47 mayfurther comprising allowing 55 the mobility procedure or the sessionprocedure without an 5 adjustment needed if the QoS parameter associatedwith the source serving network and the maximum allowed QoS of thetarget serving network are equal. The instructions unit 317 may beconfigured to perform the allowing 57.

Example Operation 58

According to some of the example embodiments, the PGW 110 network nodeis configured to receive 57 a maximum allowed QoS of a target servingnetwork, from the target MME 121 or the target S4-SGSN 126 network node,for adjusting an allowed QoS associated with a PDN connection of a userequipment 130 requesting the mobility procedure or the sessionprocedure. It should further be appreciated that the example operationmay further comprise that maximum allowed QoS of the target servingnetwork sent from Gn/Gp-SGSN directly to PGW, or to GGSN node. Thereceiving port 407 is configured to perform the receiving 58. It shouldbe appreciated that the received information may be in the form of acommunications message, for example message 7 of FIG. 4.

Example Operation 59

According to some of the example embodiments, the PGW/GGSN or PCRFnetwork node is configured to adjust 59 a QoS associated with the PDNconnection of the user equipment based on the maximum allowed QoS of thetarget serving network and the QoS parameter associated with the sourceserving network. The adjustment unit 415 is configured to perform theadjusting 59.

Example Operation 60

According to some of the example embodiments, the PGW/GGSN or PCRFnetwork node may be further configured to send 60, to a to a source MMEor a source SGSN node, a PGW, or a Policy and Charging Rules Function,PCRF, capability information element, the capability information elementindicating if the PGW 110 and/or a PCRF 105 node supports maximumallowed QoS handling. The sending 60 may occur during a previousmobility or previous session procedure. For example, the previousmobility or session procedure may occur when the source MME or sourceSGSN is functioning as a target node. The transmitting port 408 may beconfigured to perform the sending.

Conclusion

Some examples of advantages of the example embodiments described hereinmay be, if the information of ‘PGW/PCRF capability’ is sent to thetarget S4-SGSN/MME then the target MME/S4-SGSN will have the knowledgeof whether or not there is a use send the ‘Max allowed QoS’ to the PGW.In other proposed solutions, the maximum allowed QoS of the targetsystem is always sent. Therefore, the example embodiments aid in thereduction of unnecessary messages being sent. In the other case theremight be a reason for a rejection of the PDN connection or disconnect ofthe PDN connection towards the user equipment.

For Attach procedures, the target S4-SGSN/MME may get the ‘PGW/PCRFcapability’ and if the subscribed QoS values are larger than the currentnetwork max allowed (‘Max allowed QoS’), the PDN connection will beallowed to be established. Otherwise, if the PDN-GW does not support‘Max allowed QoS’ then there is a risk the PDN connection will berejected by MME or SGSN. Similarly, the same example may also beapplicable for Tracking area Update procedures, Routing area updateprocedures, and handover procedures. As SGW stores ‘Max allowed QoS’,then there may be less signaling on the s5/S8 interfaces.

It should be understood by the skilled in the art that “user equipment”is a non-limiting term which means any wireless device or node capableof receiving in DL and transmitting in UL (e.g. PDA, laptop, mobile,sensor, fixed relay, mobile relay or even a radio base station, e.g.femto base station). The example embodiments are not limited to LTE, butmay apply with any RAN, single- or multi-RAT. Some other RAT examplesare LTE-Advanced, UMTS, HSPA, GSM, cdma2000, HRPD, WiMAX, and WiFi.

It should also be appreciated that the QoS parameters discussed hereinmay comprise at least one of an EPS Bearer Level QoS and/or release 99QoS parameters, or any other QoS parameters known in the art.

The foregoing description of embodiments of the example embodiments,have been presented for purposes of illustration and description. Theforegoing description is not intended to be exhaustive or to limitexample embodiments to the precise form disclosed, and modifications andvariations are possible in light of the above teachings or may beacquired from practice of various alternatives to the providedembodiments. The examples discussed herein were chosen and described inorder to explain the principles and the nature of various exampleembodiments and its practical application to enable one skilled in theart to utilize the example embodiments in various manners and withvarious modifications as are suited to the particular use contemplated.The features of the embodiments described herein may be combined in allpossible combinations of methods, apparatus, modules, systems, andcomputer program products.

It should be noted that the word “comprising” does not necessarilyexclude the presence of other elements or steps than those listed andthe words “a” or “an” preceding an element do not exclude the presenceof a plurality of such elements. It should further be noted that anyreference signs do not limit the scope of the claims, that the exampleembodiments may be implemented at least in part by means of bothhardware and software, and that several “means”, “units” or “devices”may be represented by the same item of hardware.

A “device” as the term is used herein, is to be broadly interpreted toinclude a radiotelephone having ability for Internet/intranet access,web browser, organizer, calendar, a camera (e.g., video and/or stillimage camera), a sound recorder (e.g., a microphone), and/or globalpositioning system (GPS) receiver; a personal communications system(PCS) terminal that may combine a cellular radiotelephone with dataprocessing; a personal digital assistant (PDA) that can include aradiotelephone or wireless communication system; a laptop; a camera(e.g., video and/or still image camera) having communication ability;and any other computation or communication device capable oftransceiving, such as a personal computer, a home entertainment system,a television, etc.

The various example embodiments described herein is described in thegeneral context of method steps or processes, which may be implementedin one aspect by a computer program product, embodied in acomputer-readable medium, including computer-executable instructions,such as program code, executed by computers in networked environments. Acomputer-readable medium may include removable and non-removable storagedevices including, but not limited to, Read Only Memory (ROM), RandomAccess Memory (RAM), compact discs (CDs), digital versatile discs (DVD),etc. Generally, program modules may include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types. Computer-executableinstructions, associated data structures, and program modules representexamples of program code for executing steps of the methods disclosedherein. The particular sequence of such executable instructions orassociated data structures represents examples of corresponding acts forimplementing the functions described in such steps or processes.

1-24. (canceled)
 25. A method in a Packet Data Network Gateway (PGW)node for adjusting Quality of Service (QoS) during one of a mobilityprocedure and session procedure, the PGW node being comprised in a radionetwork, the method comprising: receiving a maximum allowed QoS of atarget serving network, from one of a target Mobility Management Entity(MME) and a target Serving General Packet Radio Service Support Node(SGSN) for adjusting an allowed QoS associated with a PDN connection ofa user equipment requesting one of the mobility procedure and sessionprocedure; and adjusting a QoS associated with the PDN connection of theuser equipment based on the maximum allowed QoS of the target servingnetwork and a QoS parameter associated with a source serving network.26. The method of claim 25, wherein the QoS parameter associated withthe source serving network is at least one or more of a maximum allowedQoS of the source serving network system and an authorized QoS of thesource serving network system.
 27. The method of claim 25, furthercomprising sending, to one of a source MME and one of a source SGSNnode, a PGW, and a Policy and Charging Rules Function (PCRF) capabilityinformation element, the capability information element indicating if atleast one or more of the PGW and a PCRF node supports maximum allowedQoS handling, said sending occurring during one of a previous mobilityprocedure and a previous session procedure.
 28. The method of claim 25,wherein one of the mobility procedure and session procedure is one of aRouting Area Update, a Tracking Area Update, a Handover procedure,Attach, PDN Connectivity and primary PDP context activation.
 29. APacket Data Network Gateway (PGW) node for adjusting Quality of Service(QoS) during one of a mobility procedure and session procedure, the PGWnode being comprised in a radio network, the node comprising: areceiving port configured to receive a maximum allowed QoS of a targetserving network, from one of a target Mobility Management Entity (MME)and a target Serving General Packet Radio Service Support Node (SGSN),for adjusting an allowed QoS associated with a PDN connection of a userequipment requesting one of the mobility procedure and sessionprocedure; and an adjusting unit configured to adjust a QoS associatedwith the PDN connection of the user equipment based on the maximumallowed QoS of the target serving network and a QoS parameter associatedwith a source serving network.
 30. The node of claim 29, wherein the QoSparameter associated with the source serving network is at least one ormore of a maximum allowed QoS of the source serving network system andan authorized QoS of the source serving network system.
 31. The node ofclaim 29, further comprising a transmitting port configured to sendduring one of a previous mobility procedure and a previous sessionprocedure, to one of a source MME and one of a source SGSN node, a PGW,and a Policy and Charging Rules Function, PCRF, capability informationelement, the capability information element indicating if at least oneor more of the PGW and a PCRF node supports maximum allowed QoShandling.
 32. The node of claim 29, wherein one of the mobilityprocedure and session procedure is one of a Routing Area Update, aTracking Area Update, a Handover procedure, Attach, PDN Connectivity andprimary PDP context activation.